The Hypertrieve database engine is a highly efficient, object-oriented database that is developed by BlueCielo ECM Solutions and embedded into Meridian Enterprise. It is optimized for use with Meridian and provided so that Meridian customers can implement engineering content management system without the need for additional software.
When you create a new Hypertrieve vault, you are given a choice of multiple Hypertrieve database engines. The first generation Hypertrieve database engine is no longer available. The database engines with names that end with the number 3 are second generation engines that have been extensively optimized compared to the first generation, particularly for 64-bit processors. The database engines with names that end with the number 5 are third generation engines that have been optimized for scalability compared to the previous generations. This optimization is primarily through the use of multithreading and for use with the Use HyperCache option described in Configuring HyperCache.
Before migrating an existing vault to Hypertrieve 5, first consider the other optimization techniques described in Optimizing performance , especially the HyperCache option, which usually boosts system performance significantly.
To determine if Hypertrieve 5 can provide additional benefits over Hypertrieve 3:
Run the Windows Performance Monitor for several working days as described in Configuring the Windows Performance Monitor. Select all performance counters for the process AMEDMW.exe and all counters in the HyperTrieve group.
Review the collected data for the following:
Note The counter represents the total capacity of all CPUs/cores. For example, on a 4 processor computer, full utilization of 1 CPU/core is shown as 25%.
If performance monitoring reveals that both of the preceding conditions occur frequently, then it is likely that Hypertrieve 5 will benefit your system. Hypertrieve 5 will make much better use of the available hardware by spreading the system load over all available processors/cores. Meridian will then provide faster and more consistent response times to its users. With other Hypertrieve versions, the user response times are highly correlated with the load on the single processor/core that is used.
Notes
Hypertrieve requires very little system administration and, in fact, has no database management user interface. The data files for a vault stored in Hypertrieve reside in the location specified when the vault was created, C:\BC-Meridian Vaults by default. Each of the Hypertrieve files are named <VaultName>.* where each file extension is described in the following table.
File Extension | Description |
---|---|
.csv |
Progress information for a stopped batch import so that the import may be resumed at a later time. |
.hdb |
Main data file. This file is always open when the EDM Server service is running. |
.lck |
Database lock file. This file is always present when the .hdb file is open by the EDM Server service. |
.log |
Transaction log file. This file accumulates document property changes until one of these events occurs:
When one of these events occurs, the contents of the log file are committed to the .hdb file, a new snapshot is generated and an empty log file is initialized. |
.snp |
The last snapshot file created either by the Minimum snapshot interval option or a Prepare for Backup operation. |